erwin Data Modeler Generative AI data sharing, privacy and protection methods - FAQ

Category

What erwin DM Delivers

AI Modeling Capabilities

AI transforms plain-language requirements into structured models using LLMs. It can auto-generate entities, attributes, relationships, metadata, business terms, and DDL scripts.

Integration & Modernization

Supports SQL, NoSQL, Snowflake, BigQuery, Databricks, MongoDB. Recommendations for migrations and ER360 integration are planned.

Authentication & Access Control

Access via SSO, LDAP, or Azure AD. AI usage is managed per license and can be disabled or blocked at the organization level.

Encryption & Data Security

Data is encrypted in transit (TLS 1.2+) and at rest (AES-256, FIPS 140-2). No data is stored by erwin DM.

Prompt Privacy & Data Handling

Prompts/responses are not stored externally. Feedback submissions are optional. Microsoft’s terms protect against training use.

Infrastructure & Hosting

AI models are hosted in the U.S. East region. Data residency control is not available. SLA uptime is 99.90%.

Governance & Compliance

Compliant with GDPR and CCPA. Prompts are never used for training. AI does not auto-detect sensitive data.

Explainability & Trust

AI does not currently explain its suggestions. Human validation and transparency controls are planned.

Future Roadmap

Upcoming features include conversational modeling, natural language queries, and Agentic AI for enterprise-scale governance.

Frequently Asked Questions (FAQ)

erwin DM uses the GPT-4 base model, deployed within Microsoft Azure.

No, prompt data is not stored or reused by OpenAI.

Yes, only the user’s email and license number are stored.

All data processing takes place in U.S. regions within Quest’s Azure environments.

Yes, it can be disabled.

It is powered by GPT-4.

Because OpenAI does not use this data to train their models.